Gathering configuration settings from a source system to apply to a target system

ABSTRACT

Provided are a method, system and program for gathering configuration settings from a source system to apply to a target system. A source system is queried to determine configuration settings in the source system. A target system is queried to determine configuration settings in the target system. A user is enabled to enter configuration settings. The determined and user entered configuration settings are processed to generate commands to configure the target system to implement the configuration settings in the source system. The generated commands are executed to configure the target system.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to a method, system, and program forgathering configuration settings from a source system to apply to atarget system.

2. Description of the Related Art

In migrating to a new computer system from a same or different vendor,the user must reconfigure the new system to include settings from thesource or older system. Such settings may include the source system'sview of attached storage devices, source hardware, such as adaptors,source applications, etc. This reconfiguration process may take asubstantial amount of time and may discourage customers from purchasingand deploying an upgraded system.

Further, in certain environments, such as for enterprise storageservers, the configuration settings the user must configure may includenumerous complex settings concerning attached storage, volumes, logicalunits, adaptor settings of how multiple adaptors connect to differenthost systems, communication settings of how the storage servercommunicates on the network, etc. A manual reconfiguration of anenterprise class storage server can take more than two weeks of persondays. Further, the vendor may have to provide substantial customersupport to assist the customer with the reconfiguration of the newsystem. Such customer support may be quite expensive for complexupgrades, such as for enterprise storage servers, which requireassistance from highly skilled and knowledgeable customer supporttechnicians.

For these reasons, there is a need in the art for improved techniques tomigrate configuration settings from a source to a target system.

SUMMARY

Provided are a method, system and program for gathering configurationsettings from a source system to apply to a target system. A sourcesystem is queried to determine configuration settings in the sourcesystem. A target system is queried to determine configuration settingsin the target system. A user is enabled to enter configuration settings.The determined and user entered configuration settings are processed togenerate commands to configure the target system to implement theconfiguration settings in the source system. The generated commands areexecuted to configure the target system.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an embodiment of a computing environment.

FIG. 2 illustrates an embodiment of a migrator database.

FIG. 3 illustrates an embodiment of an illustration of the process of amigrator program transferring configuration settings from a sourcesystem to a target system.

FIG. 4 illustrates an embodiment of operations performed by a migratorprogram to gather configuration settings from a source and targetsystems and applying the configuration settings to the target system.

DETAILED DESCRIPTION

FIG. 1 illustrates an embodiment of components in a migrationenvironment. A source system 2 comprises a system having varioussettings, including source copy service settings 4, source volumesettings 6, source physical storage settings 8, source adaptor settings10, and source application settings 12 for source applications 14installed on the source system 2. The source system 2 includes hostadaptors 16 to communicate with attached host systems (not shown), wherethe host systems access storage systems 18 through the source system 2.

The source copy service settings 4 indicate a copy service implementedin the source system 2, such as one of the applications 14, implementinga copy operation between primary and secondary designated volumes orother storage units in the storage systems 18. The copy operation maycomprise synchronous copy operations, e.g., peer-to-peer, asynchronouscopy operations, e.g., remote copy, etc. The source volume settings 6indicate a logical configuration configured in the storage systems 18,including volume identifiers of logical volumes, volume size,identifiers of logical units in which the volumes are configured,applications in the source system that use the volumes, pools in whichthe volume is included, volume capacity, etc. The source physicalstorage settings 8 may indicate the physical configuration of thestorage systems 18, e.g., Redundant Array of Independent Disk (RAID)rank information, disk devices assigned to the storage, etc. The sourceadaptor setting 10 include settings of the configuration of the hostadaptors 16 at the source system 2, such as a host name that isconnected to that host adaptor 16, and adaptor identifier (ID), anadaptor alias, a port group ID and port ID of ports configured in theadaptor, etc. The source application settings 12 provide applicationspecific settings for applications 14 installed on the source system 2.

In described embodiments, the configuration settings in the sourcesystem 2 are to be migrated to a target system 20. The target system 20includes various configuration settings including target volume settings22 indicating volume identifiers of volumes, identifiers of logicalunits in which the volumes are configured, pools in which the volume isincluded, volume capacity, etc. The target physical storage settings 24may indicate the physical configuration of the storage, e.g., RedundantArray of Independent Disk (RAID) rank information, disk devices assignedto the storage, etc. The target adaptor setting 26 include settings ofthe configuration of host adaptors 28 at the target system 20, such as ahost name that is connected to that host adaptor, an adaptor identifier(ID), an adaptor alias, a port group ID and port ID of ports configuredin the adaptor, etc. The target system 20 further includes targetapplication 30.

A migration system 32 includes a migrator program 34 that manages theconfiguration of the target system 20 to implement the configurationsettings of the source system 2. The migrator 34 gathers configurationsettings 4, 6, 8, 10, and 12 from the source system 2 and configurationsettings 20, 22, and 24 from the target system 18. The migrator 34 maygather the configuration settings by executing commands, such as commandline interfaces, on the source 2 and target 18 systems that query datastructures, databases and programs to gather the configuration settings.The migrator 34 may further communicate an electronic request forinformation to a user to enable the user to enter further information onthe source and target configuration settings to supplement theinformation the migrator 34 gathers by executing programs and commands.All the gathered information is stored in a migrator database 36. Themigrator 34 may generate a graphical user interface (GUI) 38 to enable auser to review, enter, and modify information on source 2 and target 20system configuration setting information being presented to the migrator34. Further, the migrator 34 may generate reports 38 on theconfiguration settings and a plan of how the migrator 34 will configurethe target system 18 to implement the configuration settings 4-12 of thesource system 2. The migrator 34 further generates configuration scripts42 comprising commands and program calls to configure programs (e.g.,the applications 30), hardware (e.g., the target host adaptors 28,storage adaptors, etc.), and settings in the target system 20 toimplement the configuration settings in the source system 2.

The source system 2 and target system 20 may communication with thestorage systems 18 via a direct connection or over a network, such as aWide Area Network (WAN), Local Area Network (LAN), Storage Area Network(SAN), wireless network, the Internet, an Intranet, peer-to-peernetwork, etc. Further, the migrator system 30 may communicate with thesource system 2 and target system 20 via direct connections or over anetwork, which may comprise the same or different network the source 2and target 20 systems use to communicate with the storage systems 18.The storage system 18 may comprise storage devices known in the art,such as a storage system including a plurality of storage devices, e.g.,interconnected hard disk drives (a Redundant Array of Independent Disks(RAID), Just a Bunch of Disks (JBOD), Direct Access Storage Device(DASD), disks connected in a loop configuration (serial loop, FibreChannel Arbitrated Loop), a tape library, an optical library, a networkattached storage (NAS), etc.

The migrator database 36 has data structures or records includingperformance policy information 50 comprising user defined policies thatmay be associated with applications 14, such as specifying a redundancyand performance of hardware resources allocated to the application,including storage 18 and adaptor 16 resources; copy policy information52 identifying defined copy policies, such as peer-to-peer copyrelationship, remote copy relationships, etc. for source and targetvolumes in the storage systems 18 that are subject to a copyrelationship managed by the source system 2; application information 54providing configuration settings 12 for the source applications 14installed on the source system 2; volume information 56 comprising alogical configuration of volumes and other logical devices configured inthe storage system 18 accessible to the source system 2; adaptorinformation 58 comprising the source 10 and target 26 adaptorconfiguration settings, such as the adaptor ID, host names of one ormore hosts that connect to the adaptor ID, port information, etc.;communication information 60 such as the network address, e.g., IPaddress, of the source system 2, passwords, user identifiers, etc.; andphysical storage information 62 indicating the physical configuration ofthe storage systems 18, such as a RAID configuration, number of disks,parameters of disks in the attached storage systems 18, etc.

In one embodiment, the user may define performance policy levels, e.g.,gold, bronze, platinum, etc., where each performance policy leveldefines a certain amount of hardware resource, e.g., adaptor, network,storage, redundancy and performance. An application may then beprovisioned hardware resources, e.g., storage, adaptors, networkconnectivity, etc., defined by the performance policy level.

FIG. 3 illustrates an embodiment of the process for transforming sourcedependent configuration settings to target system dependentconfiguration settings. The migrator 34 obtains source dependentconfiguration tables 80 having information on the source configurationsettings 4, 6, 8, 10, and 12 in source dependent data structures, i.e.,the tables used by the operating system and applications in the sourcesystem 2. The migrator 34 transforms the configuration information inthe source dependent configuration tables 80 into source independentconfiguration tables 82 that are not dependent on the source system 2operating system and programs. The migrator 34 then transforms theconfiguration settings in the source/target independent configurationtables 82 to target dependent configuration tables 84 that may beinstalled on the target system 29 or used to configure the target system20. For instance, the source 2 and target 20 systems may initialize andstore configuration settings in different formats and data structures.The source 80 and target 84 dependent configuration tables would conformto the specific structure and format used by the source 2 and target 20systems, respectively, to store configuration settings.

In one embodiment, the source 2 and target 20 systems may comprisestorage servers, such as enterprise storage servers, that have differentstorage server operating systems. The different source 2 and target 20systems may comprise different versions of a storage server system froma same vendor or different storage server operating systems fromdifferent vendors. The migrator 34 is coded with information to mapconfiguration settings from the source system 2 dependent configurationtables and data structures 80 to source/target independent configurationtables 82 and then to target dependent configuration tables 84. Further,the migrator 34 is coded with information to map a format of volumes andstorage in the source system 2 to the format of volumes and storage 20recognized by the target system 20. This may involve the migrator 34changing the size and format of source volumes to meet the requirementsof the target volumes.

FIG. 4 illustrates an embodiment of operations performed by the migrator34 to transfer source configuration settings 2, 4, 6, 8, 10, and 12 tothe target system 20. Upon the migrator 34 being invoked (at block 100),the migrator 34 executes (at block 102) commands on the source system 2to gather information on the user profile, attached adaptors 10, logicalvolume settings 6, physical storage configuration 8, communicationinformation, etc. The gathered source configuration settings may bemaintained in source dependent configuration tables 80. The migrator 34further executes (at block 104) commands on the target system 20 (orqueries the user) to gather information on attached adaptors 28, logicalvolume settings 22, and physical storage configuration 24 at the targetsystem 20. In one embodiment, the migrator 34 may use command lineinterfaces (CLI) of the source system 2 and target system 20 to accesstheir configuration settings. The migrator 34 further renders (at block106) a form in the GUI 38 to a user to receive user input on source andtarget configuration settings in the source/target independentconfiguration tables 82 not determined by executing the commands atblocks 102 and 104. For instance, certain of the information on thesource or target volume settings 6, 22, physical storage settings 8, 24,adaptor settings 10, 26, application settings 12, performance policiesat the source system 2, communication information 60 for the sourcesystem 2, etc., may need to be provided by the user through the GUI 38by entering information in a computer readable form that may beprocessed by the migrator 34. The rendered form includes (at block 108)input fields for a user to enter performance settings 50 and copyservice information 52 on copy relationships between volumes configuredin the connected storage systems 18.

The migrator 34 adds (at block 110) gathered configuration settings fromexecuting commands and user input to the migrator database 26. Themigrator 34 maps user entered configuration information maintained inthe migrator database 26 to source/target independent tables 82 (copypolicy information, performance policy information). The migrator 34maps (at block 112) the gathered configuration information (fromexecuting the commands and user input) to the source/target independenttables 82 (copy policy information, performance policy information) tosupplement the information determined by executing the commands atblocks 102 and 104. The migrator 34 may further present (at block 114)the source/target independent tables 82, i.e., reports 40, having thesource and target configuration settings to the user via the GUI 38 forthe user to review and modify via the GUI. The migrator 34 maps (atblock 116) information in source/target independent configuration tables82 to target dependent configuration tables 84, transforming theinformation when necessary. For instance, the source volume settings,adaptor settings, etc. may be mapped to the data structures orconfiguration tables used in the target system 20 for such configurationsettings. In one embodiment, the target system may maintain a differentformat for certain configuration settings, such as the volume settings.In such case, the migrator 34 is coded to transform source configurationsettings to the format used by the target system. The migrator 34 thengenerates (at block 118) configuration scripts 42 having commands toconfigure the target storage system 20 with the configuration settingsindicated in the system independent tables 82 (profile, volume, physicalstorage, adaptors, applications, policy settings, copy services, etc.).For instance, the configuration script 42 may set-up a copy relationshipwith a copy application 30 to implement the copy operations specified inthe source copy service settings 4, creating target copy servicesettings. The configuration scripts 42 may further execute commands toupdate the target volume settings 22, target physical storage settings24, target adaptor settings 26, application settings, etc. according tothe target dependent configuration tables 84. The configuration scripts42 may include command line interface (CLI) commands recognized by thetarget system 20 to configure the target system 20.

Described embodiments provide techniques to automatically gatherinformation on configuration settings in a source system that will beused to configure a target system to implement the configurationsettings in the source system. The migrator program may further gatherinformation on the configuration of the target system that is to bemodified with the source configuration settings. Further, the migrator34 may query the user to provide information on configuration settingsto supplement the information gathered automatically by the migrator 34.This migrator 34 accumulates all the gathered information, fromexecuting programs in the source 2 and target 20 systems and throughuser input, and then uses the gathered information to generate scriptsexecuted on the target system to configure the target system accordingto the gathered source system configuration.

By substantially automating the configuration procedure, the migratorprogram saves customers a substantial amount of time to upgrade theirsystems. Further, by reducing the opportunities for human error andautomating a substantial part of the reconfiguration process, the systemvendor substantially reduces the amount of customer support servicesthat must be provided to customers to affect the upgrade.

Additional Embodiment Details

The described operations may be implemented as a method, apparatus orarticle of manufacture using standard programming and/or engineeringtechniques to produce software, firmware, hardware, or any combinationthereof. The described operations may be implemented as code maintainedin a “computer readable medium”, where a processor may read and executethe code from the computer readable medium. A computer readable mediummay comprise media such as magnetic storage medium (e.g., hard diskdrives, floppy disks, tape, etc.), optical storage (CD-ROMs, DVDs,optical disks, etc.), volatile and non-volatile memory devices (e.g.,EEPROMs, ROMs, PROMs, RAMs, DRAMs, SRAMs, Flash Memory, firmware,programmable logic, etc.), etc. The code implementing the describedoperations may further be implemented in hardware logic (e.g., anintegrated circuit chip, Programmable Gate Array (PGA), ApplicationSpecific Integrated Circuit (ASIC), etc.). Still further, the codeimplementing the described operations may be implemented in“transmission signals”, where transmission signals may propagate throughspace or through a transmission media, such as an optical fiber, copperwire, etc. The transmission signals in which the code or logic isencoded may further comprise a wireless signal, satellite transmission,radio waves, infrared signals, Bluetooth, etc. The transmission signalsin which the code or logic is encoded is capable of being transmitted bya transmitting station and received by a receiving station, where thecode or logic encoded in the transmission signal may be decoded andstored in hardware or a computer readable medium at the receiving andtransmitting stations or devices. An “article of manufacture” comprisescomputer readable medium, hardware logic, and/or transmission signals inwhich code may be implemented. A device in which the code implementingthe described embodiments of operations is encoded may comprise acomputer readable medium or hardware logic. Of course, those skilled inthe art will recognize that many modifications may be made to thisconfiguration without departing from the scope of the present invention,and that the article of manufacture may comprise suitable informationbearing medium known in the art.

In one embodiment, the migrator program may be provided by a vendor toallow customers to migrate settings from an earlier version of a system,e.g., an earlier version of an enterprise storage server, to a morerecent version of the system. In this way, the vendor provides a toolthat makes it easier for customers to deploy the new system and reducesthe amount of time customers must spend to reconfigure the new system.

The migrator program is described as being used to copy configurationsettings between different storage server systems. In additionalembodiments, the migrator program may be used to transfer configurationsettings from different types of source systems to different types oftarget systems, such as workstations, desktop computers, mainframes,hand held computing devices, telephony devices, etc.

The terms “an embodiment”, “embodiment”, “embodiments”, “theembodiment”, “the embodiments”, “one or more embodiments”, “someembodiments”, and “one embodiment” mean “one or more (but not all)embodiments of the present invention(s)” unless expressly specifiedotherwise.

The terms “including”, “comprising”, “having” and variations thereofmean “including but not limited to”, unless expressly specifiedotherwise.

The enumerated listing of items does not imply that any or all of theitems are mutually exclusive, unless expressly specified otherwise.

The terms “a”, “an” and “the” mean “one or more”, unless expresslyspecified otherwise.

Devices that are in communication with each other need not be incontinuous communication with each other, unless expressly specifiedotherwise. In addition, devices that are in communication with eachother may communicate directly or indirectly through one or moreintermediaries.

A description of an embodiment with several components in communicationwith each other does not imply that all such components are required. Onthe contrary a variety of optional components are described toillustrate the wide variety of possible embodiments of the presentinvention.

Further, although process steps, method steps, algorithms or the likemay be described in a sequential order, such processes, methods andalgorithms may be configured to work in alternate orders. In otherwords, any sequence or order of steps that may be described does notnecessarily indicate a requirement that the steps be performed in thatorder. The steps of processes described herein may be performed in anyorder practical. Further, some steps may be performed simultaneously.

When a single device or article is described herein, it will be readilyapparent that more than one device/article (whether or not theycooperate) may be used in place of a single device/article. Similarly,where more than one device or article is described herein (whether ornot they cooperate), it will be readily apparent that a singledevice/article may be used in place of the more than one device orarticle or a different number of devices/articles may be used instead ofthe shown number of devices or programs. The functionality and/or thefeatures of a device may be alternatively embodied by one or more otherdevices which are not explicitly described as having suchfunctionality/features. Thus, other embodiments of the present inventionneed not include the device itself.

The illustrated operations of FIG. 4 show certain events occurring in acertain order. In alternative embodiments, certain operations may beperformed in a different order, modified or removed. Moreover, steps maybe added to the above described logic and still conform to the describedembodiments. Further, operations described herein may occur sequentiallyor certain operations may be processed in parallel. Yet further,operations may be performed by a single processing unit or bydistributed processing units.

The foregoing description of various embodiments of the invention hasbeen presented for the purposes of illustration and description. It isnot intended to be exhaustive or to limit the invention to the preciseform disclosed. Many modifications and variations are possible in lightof the above teaching. It is intended that the scope of the invention belimited not by this detailed description, but rather by the claimsappended hereto. The above specification, examples and data provide acomplete description of the manufacture and use of the composition ofthe invention. Since many embodiments of the invention can be madewithout departing from the spirit and scope of the invention, theinvention resides in the claims hereinafter appended.

1. An article of manufacture implementing code, wherein the codeexecuted to communicate with a source system and target system and causeoperations to be performed, the operations comprising: querying a sourcesystem to determine configuration settings in the source system;querying a target system to determine configuration settings in thetarget system; enabling a user to enter configuration settings;processing the determined and user entered configuration settings togenerate commands to configure the target system to implement theconfiguration settings in the source system; and executing the generatedcommands to configure the target system.
 2. The article of manufactureof claim 1, wherein the determined configuration settings from thesource and target systems include a logical and physical configurationof storage systems accessible to the source system, and whereinprocessing the determined configuration settings comprises determining aconfiguration of the target system storage to implement the logical andphysical configuration of the source system storage, and wherein thegenerated commands include commands to configure the target system toimplement the logical configuration of the source system storage.
 3. Thearticle of manufacture of claim 1, wherein the code is further incommunication with a database, and wherein the operations furthercomprise: combining the determined configuration settings from thesource and target systems and the user entered configuration settingsinto the database, wherein the configuration settings in the databaseare accessed to generate the commands.
 4. The article of manufacture ofclaim 1, wherein the determined and user entered configuration settingsinclude information on host adaptors at the source system, includingidentifiers and assignments of the host adaptors, wherein the generatedcommands include commands to configure the target system host adaptorsto use the identifiers and have the assignments of the host adaptors inthe source system as indicated in the configuration settings.
 5. Thearticle of manufacture of claim 1, wherein the determined and userentered configuration settings include information on applicationsinstalled at the source system to install in the target system, andwherein the generated commands include commands to configure theapplications on the target system with the determined and user enteredconfiguration settings for the applications as installed on the sourcesystem.
 6. The article of manufacture of claim 1, further comprising:processing the determined configuration settings for the source systemto access the configuration settings for the source system and store theconfiguration settings in a system independent data structure; andconverting the system independent data structure including theconfiguration settings of the source system into a target systemdependent data structure, wherein generating the commands comprisesgenerating commands to apply the configuration settings in the targetsystem dependent data structure to the target system.
 7. The article ofmanufacture of claim 1, further comprising: determining a copy servicepolicy implemented at the source system specifying to copy data fromsource storage locations to target storage locations; and generatingcommands to implement the determined copy service policy at the targetsystem to copy the data at the source storage locations to the targetstorage locations.
 8. The article of manufacture of claim 7, wherein thecopy service policy is determined from user input through the formindicating a type of the copy operation and source and target storagelocations used for the copy operation.
 9. The article of manufacture ofclaim 1, wherein enabling the user to enter configuration settingscomprises enabling the user to define performance policy levels, whereeach policy level defines an amount and quality of hardware resources toallocate, wherein the application assigned one performance policy levelis provisioned the hardware resources specified by the assigned policylevel.
 10. The article of manufacture of claim 9, wherein theperformance policy levels specify an amount of redundancy andperformance of storage and network related resources provisioned to anapplication assigned the policy level.
 11. A system in communicationwith a source system and a target system, wherein the system isaccessible to a user, comprising: a processor; a computer readablemedium including code executed by the processor to perform operations,the operations comprising: querying the source system to determineconfiguration settings in the source system; querying the target systemto determine configuration settings in the target system; enabling theuser to enter configuration settings; processing the determined and userentered configuration settings to generate commands to configure thetarget system to implement the configuration settings in the sourcesystem; and executing the generated commands to configure the targetsystem.
 12. The system of claim 11, wherein the determined configurationsettings from the source and target systems include a logical andphysical configuration of storage systems accessible to the sourcesystem, and wherein processing the determined configuration settingscomprises determining a configuration of the target system storage toimplement the logical and physical configuration of the source systemstorage, and wherein the generated commands include commands toconfigure the target system to implement the logical configuration ofthe source system storage.
 13. The system of claim 11, furthercomprising: a database, wherein the operations further comprisecombining the determined configuration settings from the source andtarget systems and the user entered configuration settings into thedatabase, wherein the configuration settings in the database areaccessed to generate the commands.
 14. The system of claim 11, whereinthe determined and user entered configuration settings includeinformation on host adaptors at the source system, including identifiersand assignments of the host adaptors, wherein the generated commandsinclude commands to configure the target system host adaptors to use theidentifiers and have the assignments of the host adaptors in the sourcesystem as indicated in the configuration settings.
 15. The system ofclaim 11, wherein the operations further comprise: processing thedetermined configuration settings for the source system to access theconfiguration settings for the source system and store the configurationsettings in a system independent data structure; and converting thesystem independent data structure including the configuration settingsof the source system into a target system dependent data structure,wherein generating the commands comprises generating commands to applythe configuration settings in the target system dependent data structureto the target system.
 16. The system of claim 11, wherein the operationsfurther comprise: determining a copy service policy available at thesource system specifying to copy data from source storage locations totarget storage locations; and generating commands to implement thedetermined copy services at the target system to copy the data at thesource storage locations to the target storage locations.
 17. The systemof claim 11, wherein enabling the user to enter configuration settingscomprises enabling the user to define performance policy levels, whereeach policy level defines an amount and quality of hardware resources toallocate, wherein an application assigned one performance policy levelis provisioned the hardware resources specified by the assigned policylevel.
 18. The system of claim 17, wherein the performance policy levelsspecify an amount of redundancy and performance of storage and networkrelated resources provisioned to the application assigned the policylevel.
 19. A method, comprising: querying a source system to determineconfiguration settings in the source system; querying a target system todetermine configuration settings in the target system; enabling a userto enter configuration settings; processing the determined and userentered configuration settings to generate commands to configure thetarget system to implement the configuration settings in the sourcesystem; and executing the generated commands to configure the targetsystem.
 20. The method of claim 19, wherein the determined configurationsettings from the source and target systems include a logical andphysical configuration of storage systems accessible to the sourcesystem, and wherein processing the determined configuration settingscomprises determining a configuration of the target system storage toimplement the logical and physical configuration of the source systemstorage, and wherein the generated commands include commands toconfigure the target system to implement the logical configuration ofthe source system storage.
 21. The method of claim 19, furthercomprising: combining the determined configuration settings from thesource and target systems and the user entered configuration settingsinto a database, wherein the configuration settings in the database areaccessed to generate the commands.
 22. The method of claim 19, whereinthe determined and user entered configuration settings includeinformation on host adaptors at the source system, including identifiersand assignments of the host adaptors, wherein the generated commandsinclude commands to configure the target system host adaptors to use theidentifiers and have the assignments of the host adaptors in the sourcesystem as indicated in the configuration settings.
 23. The method ofclaim 19, further comprising: processing the determined configurationsettings for the source system to access the configuration settings forthe source system and store the configuration settings in a systemindependent data structure; and, converting the system independent datastructure including the configuration settings of the source system intoa target system dependent data structure, wherein generating thecommands comprises generating commands to apply the configurationsettings in the target system dependent data structure to the targetsystem.
 24. The method of claim 19, further comprising: determining acopy service policy implemented at the source system specifying to copydata from source storage locations to target storage locations; andgenerating commands to implement the determined copy services at thetarget system to copy the data at the source storage locations to thetarget storage locations.
 25. The method of claim 19, wherein enablingthe user to enter configuration settings comprises enabling the user todefine performance policy levels, where each policy level defines anamount and quality of hardware resources to allocate, wherein anapplication assigned one performance policy level is provisioned thehardware resources specified by the assigned policy level.
 26. Themethod of claim 25, wherein the performance policy levels specify anamount of redundancy and performance of storage and network relatedresources provisioned to an application assigned the policy level.